docs: Restructure documentation with separate introduction section#771
docs: Restructure documentation with separate introduction section#771patrikbraborec wants to merge 2 commits intomasterfrom
Conversation
This reverts commit 2ed03ca.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #771 +/- ##
==========================================
- Coverage 81.91% 81.84% -0.08%
==========================================
Files 46 46
Lines 2693 2693
==========================================
- Hits 2206 2204 -2
- Misses 487 489 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
Consolidate the introduction section by merging installation info into the overview page, removing the separate installation page, and flattening the sidebar navigation. Update slugs and redirect paths to use /overview. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
|
@TC-MO I did the same changes as in JS SDK (structure-wise). Please check it. |
TC-MO
left a comment
TC-MO
left a comment
There was a problem hiding this comment.
One big ticket item - but seems that can be future work we discussed previously.
Other than that, remove gerunds from headings and we should be okay to merge this restructure & work further on the content
| The Apify SDK for Python is typically installed when you create a new Actor project using the [Apify CLI](https://docs.apify.com/cli). To install it manually in an existing project, use: | ||
|
|
||
| ```bash | ||
| pip install apify | ||
| ``` |
There was a problem hiding this comment.
I think I already mentioned it in one of the previous reviews, but why are we putting SDK installation through CLI first and foremost? This feels backwards to me, we should:
- First mention how to install it manually
- Mention that you can also utilize CLI to scaffold a project and get it installed as dependency
- Admonition about programmatic use through Client
There was a problem hiding this comment.
But then again this might be something to do quickly after we merge this restructure
| ## Quick start | ||
|
|
||
| ### Creating Actors | ||
| ## Step 1: Creating Actors |
There was a problem hiding this comment.
Please no gerund in headings
| ## Step 1: Creating Actors | |
| ## Step 1: Create Actors |
|  | ||
|
|
||
| #### Running the Actor | ||
| ## Step 2: Running the Actor |
There was a problem hiding this comment.
Please no gerund in the headings
| ## Step 2: Running the Actor | |
| ## Step 2: Run Actors |
| The Actor input, for example, will be in `storage/key_value_stores/default/INPUT.json`. | ||
|
|
||
| ## Actor structure | ||
| ## Step 3: Understanding Actor structure |
There was a problem hiding this comment.
Please no gerund in the headings
| ## Step 3: Understanding Actor structure | |
| ## Step 3: Understand Actor structure |
| To create and run Actors in Apify Console, refer to the [Console documentation](/platform/actors/development/quick-start/web-ide). | ||
|
|
||
| To create a new Apify Actor on your computer, you can use the [Apify CLI](/cli), and select one of the [Python Actor templates](https://apify.com/templates?category=python). |
There was a problem hiding this comment.
same here as above, those two should be mentioned only after we explain a simple way to interact with SDK
There was a problem hiding this comment.
but again this is further down the line after restructure
2 participants
Summary
Re-applies the documentation restructuring from #740 (which was reverted in #763).
/docs/introductionTest plan
🤖 Generated with Claude Code